This should also resolve #433

@jaromil is there a particular reason why this PR is in limbo?

Hi! Many thanks for your PR! It not in limbo, just some delay due to new year's holiday and the fact this project is ran by volunteers.

I am just wondering if the renaming to __ESC_SPACE__ is appropriate, or shall we just use a _ underscore for the generated targets used by bind mount.

The use of __ESC_SPACE__ as a placeholder in the script serves a specific purpose: it is intended to be a unique sequence that is unlikely to occur in actual file or directory names. This uniqueness is essential because the placeholder temporarily represents spaces in paths during processing to avoid issues with word splitting.

If we were to use a single underscore _, there is a real possibility that actual path names could contain underscores. These would then be erroneously converted to spaces when the placeholder is reverted, leading to incorrect path names. By using __ESC_SPACE__, we mitigate this risk because it is designed to stand out and not conflict with typical naming conventions.

Therefore, while the placeholder may seem verbose or unconventional, its distinctive pattern is a safeguard to ensure that only the intended spaces are replaced and then accurately restored, preserving the integrity of the file paths during the bind mount process.

Excellent explanation, thanks for all your attention to details and welcome among the Tomb contributors!